home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19980424-19980901
/
000276_news@newsmaster….columbia.edu _Wed Jul 15 11:22:14 1998.msg
< prev
next >
Wrap
Internet Message Format
|
1998-08-31
|
4KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id LAA15473
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 15 Jul 1998 11:22:14 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id LAA29792
for kermit.misc@watsun; Wed, 15 Jul 1998 11:22:14 -0400 (EDT)
From: heiby_u@falkor.chi.il.us (Ron Heiby)
Subject: Problems w/ 115Kbps Direct Connect - k95xfer.gif (0/1)
Date: Wed, 15 Jul 1998 15:06:52 GMT
Organization: Strategis Consulting Inc.
Message-ID: <35acb87b.1654633@149.174.211.108>
X-Newsreader: Forte Agent 1.5/32.451
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: comp.protocols.kermit.misc
Path: news.columbia.edu!sol.ctr.columbia.edu!news.indiana.edu!news2.ais.net!jamie!ais.net!WCG!arl-news-svc-3.compuserve.com!news-master.compuserve.com!nntp-ntawwabp.compuserve.com
Lines: 51
Xref: news.columbia.edu comp.protocols.kermit.misc:8976
I am having a problem with Kermit-95 1.1.17. I am seeing numerous CRC error,
Retransmission, Bad Sequence Number, etc. errors on the file transfer.
Sometimes, the transfer aborts. Sometimes it goes to completion and claims
to be successful, but the file on disk is damaged.
I am running over a direct serial cable between my desktop (Pentium) and
notebook (486DX4/100). The desktop is running as "server". When I send from
the notebook to the desktop, I have never seen a problem. When I send from
the desktop to the notebook, I am seeing these problems.
Both systems are running Windows 95. I have the serial ports set for 115200,
mode local, modem none, flow rts/cts, handshake none, block check 3. Both
using COM1 internal serial port. I have tried several receive packet lengths
from 9024 down to 1500, and seen these failures. However, when I set the
receive packet length to 1000, I have run about a dozen tests with no
problem.
I tried adding "set receive padding 94", but that seemed to have no effect
on this problem.
Sooooo... I guess I have a work-around: "set receive packet-length 1000"
when operating at high speeds, at least until I replace my notebook with
something faster.
Questions still remaining:
1) Why would I be seeing these problems? Is it some fundamental limitation
of Win95? Could my serial port not have its buffering set properly? Does
Kermit-95 set port buffering, or do I set it via Control Panel / System /
Device Manager? I tried all four settings, but had problems on every one of
them, so that doesn't seem to be it, at least by itself.
2) When these errors happen, why doesn't K95 realize what is going on, and
refrain from putting garbage into the file? Why does it indicate successful
completion of the transfer when there are bytes missing from the file? This
one is most disturbing.
3) What the heck am *I* doing wrong (if anything)?
Here is a screen capture of my Kermit-95 window from one of the more (but
not completely) successful tests at packet size 8000. Note that K95 reports
that the transfer was successful, but that the number of bytes listed in the
success report does not match the file size. The number of bytes in the
success report is the number K95 wrote to the file. The number of bytes in
the file size is the number of bytes that are *supposed* to be in the file.
Thanks!
--
Ron.